Skip to content

Conversation

emberian
Copy link
Contributor

@emberian emberian commented Jan 6, 2014

No description provided.

I don't think it's relevant, a warning is more appropriate. Easier to just
maintain the order.

Closes #4681
This let's us specify exactly which snapshot a given note to update after
snapshot is for.

Closes #2483
pcwalton says this is right, and it looks right to me too.

Closes #4731
Obviously everything is unstable, but these particularly so, and they will
likely remain that way.

Closes #10239
@emberian
Copy link
Contributor Author

emberian commented Jan 6, 2014

I removed the contentious commits; moving arg name checking to typeck turned out to be not as easy (requires walking the types of the arguments to catch duplicate names in closure decls).

bors added a commit that referenced this pull request Jan 6, 2014
@bors bors closed this Jan 6, 2014
@bors bors merged commit 2097570 into rust-lang:master Jan 6, 2014
flip1995 pushed a commit to flip1995/rust that referenced this pull request Aug 14, 2023
…p1995

Do not bless by default in ui tests

This restores the default behaviour to check the `.stderr`, it was changed in rust-lang#11239 to bless by default in `cargo test` (unless in github actions), but check by default in `cargo uitest` which is fairly confusing

It also meant `cargo uitest -F internal` no longer worked

`--bless` prevents the use of `Args::test` but we can look at reintegrating with that after `@oli-obk's` vacation

r? `@flip1995`

changelog: none
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants